Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging typos fixed, maybe one error code definition too #12054

Merged
merged 2 commits into from
Jul 23, 2024

Conversation

oljemark
Copy link
Collaborator

Fixes #12051

Status

not-tested

Description

Fixes some logging output typos, that seem not have been hardcoded into parsing code elsewhere on github (except for the second commit with 'woud's ).
Is WMCore/Agent/Flow/DefaultFlow.py used at all? I only saw it in a help output from the flow generation as a default file to modify to your own needs, not run as is? If you want, I could cherry-pick the commits from master...oljemark:WMCore:twiki-codes to this PR - the error code typo fix would also need simultaneous fix in the TWiki.

Is it backward compatible (if not, which system it affects?)

MAYBE

Related PRs

External dependencies / deployment changes

@cmsdmwmbot
Copy link

Can one of the admins verify this patch?

@amaltaro
Copy link
Contributor

test this please

@cmsdmwmbot
Copy link

Jenkins results:

  • Python3 Unit tests: failed
    • 1 new failures
  • Python3 Pylint check: failed
    • 99 warnings and errors that must be fixed
    • 42 warnings
    • 771 comments to review
  • Pylint py3k check: failed
    • 2 warnings
  • Pycodestyle check: succeeded
    • 212 comments to review

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-WMCore-PR-test/15115/artifact/artifacts/PullRequestReport.html

Copy link
Contributor

@amaltaro amaltaro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes are looking good to me as well, but there is one module that needs to be updated (please see my comment along the code).

Once you make that change, could you please squash the new commit into the first one? In case you need some directions on that process, I find this https://steveklabnik.com/writing/how-to-squash-commits-in-a-github-pull-request a good source. Thank you again!

src/python/WMComponent/JobCreator/JobCreatorPoller.py Outdated Show resolved Hide resolved
@oljemark
Copy link
Collaborator Author

Hello. Fixed now, if you meant for the 2nd commit to remain separate.

@amaltaro
Copy link
Contributor

Great, thanks Fredrik!
Ideally, the 2nd commit would have only test/* changes, as mentioned in the contributing guidelines. But I appreciate your prompt fix and it is good to go!

@amaltaro amaltaro merged commit bd337e7 into dmwm:master Jul 23, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants